Fix detection of 64-bit for Visual Studio 2019 and 2022 #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Visual Studio 2017 and earlier, if
CMAKE_GENERATOR_PLATFORMwas not specified, the build defaulted to 32-bit, hence_ARCHwas to set tox86ifCMAKE_GENERATOR_PLATFORMwas not set with MSVC. However, since Visual Studio 2019 ifCMAKE_GENERATOR_PLATFORMis not specified, the build defaults to 64-bit, see https://cmake.org/cmake/help/latest/generator/Visual%20Studio%2016%202019.html .This patch ensure that 64-bit is correctly used for builds using Visual Studio 2019 and greater.